View CT1990-1-20_1602084.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

eroflex circuit t echnology ? data bus modules for the future ? scd1990 rev b 8/21/00 features ? performs the complete dual-redundant remote terminal, bus controller protocol and passive monitor functions of mil-std-1553b ? automated self-test functions ? allows setting of the message error bit on illegal commands ? provides programmable control over terminal flag and subsystem flag status bits ? mil-prf-38534 compliant circuits available ? 50 mw typical power consumption ? small size ? available in ceramic plug-in package configuration ? compatible with all act driver/receiver units ? 5v dc operation ? full military (-55c to +125c) temperature range ? desc smd# 5962?94775: released ct1990, pending ct1991 1 general description the ct1990/1 series is a monolithic implementation of the mil-std-1553b bus controller, remote terminal and passive monitor functions. all protocol functions of mil-std-1553b are incorporated and a number of options are included to improve flexibility. these features include programming of the status word, illegalizing specific commands and an independent loop back self-test which is initiated by the subsystem. this unit is directly compatible with all transceivers and microprocessor interfaces such as the ct1611 and ct1800 produced by aeroflex incorporated. encoder decoder "o" decoder "1" driver select & enable bus "0" bus "1" t/r hybrid t/r hybrid internal highway control interface unit program sub address & word count outputs discrete outputs control inputs terminal address inputs block diagram (with transformers) circuit technology ct1990/1 mil-std-1553b remote terminal, bus controller, or passive monitor hybrid with status word control ct1990/1 series inputs status word control
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 2 absolute maximum ratings parameter range units supply voltage (v d d ) -0.3 to +7.0 v input or output voltage at any pad -0.3 to (v d d + 0.3) v storage case temperature -65 to +150 c recommended dc operating conditions parameter min typ max unit notes vcc power supply voltage vcc 4.5 5.0 5.5 v - v ih high level input voltage, vcc = 5v 2.2 v 1,2 v il low level input voltage, vcc = 5v 0.7 v 1,2 electrical characteristics (t a = -55 c to +125c) parameter test conditions min max unit notes v oh high level output voltage vcc = 4.5v 2.4 v 4 v ol low level output voltage vcc = 4.5v 0.4 v 4 i ih high level input current vcc = 5.5v, v i n = 2.4v -200 -25 -700 -400 a a 2 3 i il low level input current vcc = 5.5v, v i n = 0.4v -400 -25 -900 -400 a a 2 3 i cc supply current vcc = 5.5v 20 ma 4 notes: 1. rtad 0/1/2/3/4 and rtadpar only. 2. all inputs and bidirectionals other than those in note 1. 3. l o l max = 3ma / l o h max = -2ma tx inhibit 0/1 and tx data/ data only. i o l max = 2ma / l o h max = -1 ma. all remaining outputs and bidirectionals. 4. input clock (running) = 6mhz, all remaining inputs are open and all outputs and bidirectionals have no load. clock requirements frequency 6.0 mhz stability -55c to +125c 0.01% (100ppm) maximum asymmetry 48 - 52% rise/fall time 10ns max output level logic "0" 0.4v max logic "1" 2.4v min
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 3 remote terminal operation receive data operation all valid data words associated with a valid receive data command word for the rt are passed to the subsystem. the rt examines all command words from the bus and will respond to valid (i.e. correct manchester, parity coding etc.) commands which have the correct rt address (or broadcast address if the rt broadcast option is enabled). when the data words are received, they are decoded and checked by the rt and, if valid, passed to the subsystem on a word by word basis at 20 s intervals. this applies to receive data words in both bus controller to rt and rt to rt messages. when the rt detects that the message has finished, it checks that the correct number of words have been received and if the message is fully valid, then a good block received signal is sent to the subsystem, which must be used by the subsystem as permission to use the data just received. the subsystem must therefore have a temporary buffer store up to 32 words long into which these data words can be placed. the good block received signal will allow use of the buffer store data once the message has been validated. if a block of data is not validated, then good block received will not be generated. this may be caused by any sort of message error or by a new valid command for the rt being received on another bus to which the rt must switch. transmit data operation if the rt receives a valid transmit data command addressed to the rt, then the rt will request the data words from the subsystem for transmission on a word by word basis. to allow maximum time for the subsystem to collect each data word, the next word is requested by the rt as soon as the transmission of the current word has commenced. it is essential that the subsystem should provide all the data words requested by the rt once a transmit sequence has been accepted. failure to do so will be classed by the rt as a subsystem failure and reported as such to the bus controller. control of data transfers this section describes the detailed operation of the data transfer mechanism between the rt and subsystems. it covers the operations of the signals dtrq , dtak , iustb, h/ l , gbr , nbgt , tx/ rx during receive data and transmit data transfers. figure 7 shows the operation of the data handshaking signals during a receive command with two data words. when the rt has fully checked the command word, nbgt is pulsed low, which can be used by the subsystem as an initialization signal. tx/ rx will be set low indicating a receive command. when the first data word has been fully validated, dtrq is set low. the subsystem must then reply within approximately 1.5 s by setting dtak low. this indicates to the rt that the subsystem is ready to accept data. the data word is then passed to the subsystem on the internal highway ih08-ih715 in two bytes using iustb as a strobe signal and h/ l as the byte indicator (high byte first followed by low byte). data is valid about both edges of iustb. signal timing for this handshaking is shown in figure 12. if the subsystem does not declare itself busy, then it must respond to dtrq going low by setting dtak low within approximately 1.5 us. failure to do so will be classed by the rt as a subsystem failure and reported as such to the bus controller. it should be noted that iustb is also used for internal working in the rt. dtrq being low should be used as an enable for clocking data to the subsystem with iustb. once the receive data block has finished and been checked by the rt, gbr is pulsed low if the block is entirely correct and valid. this is used by the subsystem as permission to make use of the data block. if no gbr signal is generated, then an error has been detected by the rt and the entire data block is invalid and no data words in it may be used. if the rt is receiving data in an rt to rt transfer, the data handshaking signals will operate in an identical fashion but there will be a delay of approx 70 s between nbgt going low and dtrq first going low. see figure 10.
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 4 figure 6 shows the operation of the data handshaking signals during transmit command with three data words. as with the receive command discussed previously, nbgt is pulsed low if the command is valid and for the rt. tx/ rx will be set high indicating a transmit data command. while the rt is transmitting its status word, it requests the first data word from the subsystem by setting dtrq low. the subsystem must then reply within approximately 13.5 s by setting dtak low. by setting dtak low, the subsystem is indicating that it has the data word ready to pass to the rt. once dtak is set low by the subsystem, dtrq should be used together with h/ l and tx/ rx to enable first the high byte and then the low byte of the data word onto the internal highway ih08-ih715. the rt will latch the data bytes during iustb, and will then return dtrq high. data for each byte must remain stable until iustb has returned low. signal timing for this handshaking is shown in figure 11. additional data information signals at the same time as data transfers take place, a number of information signals are made available to the subsystem. these are incmd , the subaddress lines sa0-sa4, the word count lines wc0-wc4 and current word count lines cwc0-cwc4. use of these signals is optional. incmd will go active low while the rt is servicing a valid command for the rt. the subaddress, transmit/receive bit, and word count from the command word are all made available to the subsystem as sa0-sa4, tx/ rx and wc0-wc4 respectively. they may be sampled when incmd goes low and will remain valid while incmd is low. the subaddress is intended to be used by the subsystem as an address pointer for the data block. subaddress 0 and 31 are mode commands, and there can be no receive or transmit data blocks associated with these. (any data word associated with a mode command uses different handshaking operations. if the subsystem does not use all the subaddresses available, then some of the subaddress lines may be ignored. the tx/ rx signal indicates the direction of data transfer across the rt - subsystem interface. its use is described in the previous section. the word count tells the subsystem the number of words to expect to receive or transmit in a message, up to 32 words. a word count of all 0s indicates a count of 32 words. the current word count is set to 0 at the beginning of a new message and is incremented following each data word transfer across the rt - subsystem interface. (it is clocked on the falling edge of the second iustb pulse in each word transfer). it should be noted that there is no need for the subsystem to compare the word count and current word count to validate the number of words in a message. this is done by the rt. subsystem use of status bits and mode commands general description use of the status bits and the mode commands is one of the most confusing aspects of mil-std-1553b. this is because much of their use is optional, and also because some involve only the rt while others involve both the rt and the subsystem. the ct1990/1 allows full use to be made of all the status bits, and also implements all the mode commands. external programming of the terminal flag and subsystem flag bits plus setting of the message error bit on reception of an illegal command when externally decoded is available. the subsystem is given the opportunity to make use of status bits, and is only involved in mode commands which have a direct impact on the subsystem. the mode commands in which the subsystem may be involved are synchronize, sychronize with data word, transmit vector word, reset and dynamic bus control acceptance. the status bits to which the subsystem has access, or control are service request, busy, dynamic bus control acceptance, terminal flag, subsystem flag, and message error bit. operation of each of these mode commands and of the status bits is described in the following sections. all other mode commands are serviced internally by the rt. the terminal flag and message error status bits and bit word contents are controlled by the rt; however the subsystem has the option to set the message error bit and to control the reset conditions for the terminal flag and subsystem flag bits in the status word, and the transmitter timeout, subsystem handshake, and loop test fail bits in the bit word.
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 5 synchronize mode commands once the rt has validated the command word and checked for the correct address, the sync line is set low. the signal wc4 will be set low for a synchronize mode command (see figure 16), and high for a synchronize with data word mode command (see figure 15). in a synchronize with data word mode command, sync remains low during the time that the data word is received. once the data word has been validated, it is passed to the subsystem on the internal highway ih08-ih715 in two bytes using iustb as a strobe signal and h/l as the byte indicator (high byte first followed by low byte). sync being low should be used on the enable to allow iustb to clock synchronize mode data to the subsystem. if the subsystem does not need to implement either of these mode commands, the sync signal can be ignored, since the rt requires no response from the subsystem. transmit vector word mode command figure 14 illustrates the relevant signal timings for an rt receiving a valid transmit vector word mode command. the rt requests data by setting vecten low. the subsystem should use h/ l to enable first the high byte and then the low byte of the vector word onto the internal highway ih08-ih715. it should be noted that the rt expects the vector word contents to be already prepared in a latch ready for enabling onto the internal highway when vecten goes low. if the subsystem has not been designed to handle the vector word mode command, it will be the fault of the bus controller if the rt receives such a command. since the subsystem is not required to acknowledge the mode command, the rt will not be affected in any way by vector word circuitry not being implemented in the subsystem. it will however transmit a data word as the vector word, but this word will have no meaning. reset mode command figure 8 shows the relevant signal timings for an rt receiving a valid reset mode command. once the command word has been fully validated and serviced, the reset signal is pulsed low. this signal may be used as a reset function for subsystem interface circuitry. dynamic bus allocation this mode command is intended for use with a terminal which has the capability of configuring itself into a bus controller on command from the bus. the line dbcreq cannot go true unless the dbcacc line was true at the time of the valid command, i.e. tied low. for terminals acting only as rts, the signal dbcacc should be tied high (inactive), and the signal dbcreq should be ignored and left unconnected. use of the busy status bit the busy bit is used by the subsystem to indicate that it is not ready to handle data transfers either to or from the rt. the rt sets the bit to logic one if the busy line from the subsystem is active low at the time of the second falling edge of inclk after incmd goes low. this is shown in figure 13. once the busy bit is set, the rt will stop all receive and transmit data word transfers to and from the subsystem. the data transfers in the synchronize with data word and transmit vector word mode commands are not affected by the busy bit and will take place even if it has been set. it should be noted that a minimum of 0.5 s subaddress decoding time is given to the subsystem before setting of status bits. this allows the subsystem to selectively set the busy bit if for instance one subaddress is busy but others are ready. this option will prove useful when an rt is interfacing with multiple subsystems. use of the service request status bit the service request bit is used by the subsystem to indicate to the bus controller that an asynchronous service is requested. the timing of the setting of this bit is the same as the busy bit and is shown in figure 13. use of servreq has no effect on the rt apart from setting the service request bit. it should be noted that certain mode commands require that the last status word be transmitted by the rt
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 6 instead of the current one, and therefore a currently set status bit will not be seen by the bus controller. therefore the user is advised to hold servreq low until the requested service takes place. use of the subsystem status bit this status bit is used by the rt to indicate a subsystem fault condition. if the subsystem sets sserr low at any time, the subsystem fault condition in the rt will be set, and the subsystem flag status bit will subsequently be set. the fault condition will also be set if a handshaking failure takes place during a data transfer to or from the subsystem. the fault condition is cleared on power-up or by a reset mode command. dynamic bus control acceptance status bit dbcacc , when set true, enables an rt to configure itself into a bus controller, if the subsystem has the capability, by allowing dbcreq to pulse true and bit time 18 to be set in the status response. if dynamic bus control is not required then dbcacc must be tied high. dbcacc tied high inhibits dbcreq and clears bit time 18 in the status response. optional status word control message error bit the ct1990/1 monitors all receptions for errors and sets the message error bit as prescribed in mil-std-1553b. the subsystem designer may, however, exercise the option of monitoring for illegal commands and forcing the message error bit to be set. the word count and subaddress lines for the current command are valid when incmd goes low. the subsystem must then determine whether or not the word count or subaddress is to be considered illegal by the rt. if either of them is considered illegal, the subsystem must produce a positive-going pulse called mereq. the positive-going edge of mereq must occur within 500 ns of the falling edge of incmd . subsystem flag and terminal flag bits the conditions that cause the subsystem flag and terminal flag bits in the status word to be reset may be controlled by the subsystem using the enable , bit decode , next statu s, and status update inputs. if enable is inactive (high), then the terminal flag and subsystem flag behavior is the same as described below: (i.e. the other three option lines are disabled). subsystem flag bit this bit is reset to logic zero by a power up initialization or the servicing of a legal mode command to reset the remote terminal (code 01000). this bit shall be set in the current status register if the subsystem error line, sserr , from the subsystem ever goes active low. this bit shall also be set if an rt/subsystem handshaking failure occurs. this bit, once set, shall be repeatedly set until the detected error condition is known to be no longer present. terminal flag bit this bit is reset to logic zero by a power up initialization or the servicing of a legal mode command to reset the remote terminal (code 01000). this bit can be set to logic one in the current status register in four possible ways: a) if the rx detects any message encoding error in the terminals transmission. a loop test failure, ltfail, will be signalled which shall cause the terminal flag to be set and the transmission aborted. b) if a transmitter timeout occurs while the terminal is transmitting. c) if a remote terminal self test fails. d) if there is a parity error in the hard wired address to the rx chip. this bit, once set, shall be repeatedly set until the detected error condition is known to be no longer present. the transmission of this bit as a logic one can be inhibited a legal mode command to inhibit terminal flag bit (code 00110). similarly, this inhibit can be removed by a mode command to override inhibit terminal flag bit (code 00111), a power up initialization or a legal mode command to reset remote terminal (code 01000).
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 7 if enable is held low, then the three options described below are available and are essentially independent. any, all, or none may be selected. also, reporting of faults by the subsystem requires that sserr be latched (not pulsed) low until the fault is cleared. resetting ssf and tf on receipt of valid commands if enable is selected and the other three option lines are held high, then the status word register will be reset on receipt of any valid command with the exception of transmit status and transmit last command. note that in this mode, the tf will never be seen in the status word, and the ssf will only be seen if sserr is latched low. also note that the ssf will not be seen in response to transmit status or transmit last command if the preceding status word was clear, regardless of actions taken on the sserr line after the clear status transmission. status register update at fault occurrence if status update is selected (held low), then the tf or ssf will appear in response to a transmit status or transmit last command issued as the first command after the fault occurs. any other command (except as noted in the preserving the bit word section) will reset the tf and ssf. repeated transmit status or transmit last command immediately following the fault will continue to show the tf and/or ssf in the status word. note that this behavior may not meet the "letter-of-the-spec" as described in mil-std-1553b, but is considered the "preferred" behavior by some users. tf and ssf reporting in the next status word after the fault if next status is selected (held low), then the tf or ssf will appear in response to the very next valid command after the fault except for transmit status or transmit last command. the flag(s) will be reset on receipt of any valid command following the status transmission with the flag(s) set except for transmit status, transmit last command, or as noted in the following section on preserving the bit word. preserving the bit word in order to preserve the transmitter timeout flag, subsystem handshake failure, and loop test failure bits in the bit word, it is necessary to select bit decode (hold it low). this will prevent resetting those bits if the transmit bit word mode command immediately follows the fault or follows a transmit last command or transmit status immediately following the fault. it will also prevent resetting the tf and ssf bits in the status word. any other valid commands will cause those bit word bits and the status word bits to be reset. bus driver/receiver interface receive data the decoder chip requires two ttl signals, rxdata and rxdata , to represent the data coming in from the bus. pdin should be driven to a logic level ?1? when the bus waveform exceeds a specified positive threshold and ndin should be driven to a logic level ?1? when a specified negative threshold is exceeded. during the quiet period on the bus both signals should be at the same logic level. all the bus receivers must be permanently enabled, the selection of the bus in use is controlled within the asic. transmit data the signals generated by the encoder chip, txdata and txdata, are of the same format as the receive data. the only difference is that the ttl signals are negative logic, e.g. the signal is active when on logic level "0". this means that when the encoder is quiet both txdata and txdata are at logic level "1". both the signals should be used in conjunction with txinhibit 0 and txinhibit 1. tx inhibit 0 and tx inhibit 1 enable the appropriate driver when it should be transmitting. figure 5 shows an example of a typical interface circuit between the ct1990/1 and a driver/receiver unit.
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 8 bus control operation to enable its use in a bus controller the asic has additional logic within it. this logic can be enabled by pulling the pin labelled rt/ bc low. once the asic is in bus control mode, all data transfers must be initiated by the bus control processor correctly commanding the asic via the subsystem interface. in bus control mode six inputs are activated which in rt mode are inoperative and four signals with dual functions exercise the second function (the first being for the rt operation). to use the ct1990/1 as a 1553b bus control interface, the bus control processor must be able to carry out four basic bus-related functions. two inputs, bcopa and bcopb allow these four options to be selected. the option is then initiated by sending a negative-going strobe on the bcopstb input. bcopstb must only be strobed low when ndrq is high. this is particularly important when two options are required during a single transfer. with these options all message types and lengths can be handled. normal bc/rt exchanges are carried out in asic option zero. this is selected by setting bcopa and bcopb to a zero and strobing bcopstb . on receipt of the strobe, the ct1990/1 loads the command word from an external latch using cwen and h/l the command word is transmitted down the bus. the tx/ rx bit is, however, considered by the asic as being its inverse and so if a transmit command is sent to a rt (figure 17), the asic in bc mode believes it has been given a receive command. as the rt returns the requested number of data words plus its status, the bc carries out a full validation check and passes the data into the subsystem using dtrq , dtak , h/ l , iustb and cwc as in rt operation. it also supplies gbr at the end of a valid transmission. conversely, a receive command sent down the bus is interpreted by the bc as a transmit command, and so the requisite data words are added to the command word. see figure 18. for mode commands, where a single command word is required, option one is selected by strobing bcopstb when bcopa is high and bcopb is low. on receiving the strobe, the command word is loaded from the external latch using cwen and h/ l , the correct sync and parity bits are added and the word transmitted (see figure 20). mode commands followed by a data word requires option two. option two, selected by strobing bcopstb while bcopa is low and bcopb is high, loads a data word via dwen and h/ l , adds sync and parity and transmits them to the bus (see figure 21). if the mode code transmitted required the rt to return a data word, then selecting option three by strobing bcopstb when bcopa and bcopb are both high will identify that data word and if validated, output it to the subsystem interface using rmdstb and h/ l. this allows data words resulting from mode codes to be identified differently from ordinary data words and routed accordingly (see figure 22). all received status words are output to the subsystem interface using statstb and h/ l . in bc option three, if the signal pasmon is active, then all data appearing on the selected bus is output to the subsystem using statstb for command and status words or rmdstb for data words. rt to rt transfers require the transmission of two command words. a receive command to one rt is contiguously followed by a transmit command to the other rt. this can be achieved by selecting option one followed by option zero for the second command. the strobe ( bcopstb ) for option zero must be delayed until ndrq has gone low and returned high following the strobe for option one. the rt transmissions are checked and transferred in the subsystem interface to the bus control processor (see figure 19). note: for all bc operations, bcopa and bcopb must remain valid and stable for a minimum of 1 s following the leading (negative going) edge of bcopstb . passive monitor the monitor mode may be utilized to analyze or collect all activities which occur on a selected bus. this is initiated by selecting a bus, placing the unit in bc option three and setting pasmon low. all data appearing on the selected bus is output to the subsystem using statstb for command and status words or rmdstb for data words.
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 9 automated self-test the ct1991 has been designed to fully support a wrap-around self-test which ensures a high degree of fault coverage. the monolithic circuit includes all circuitry required to perform the self-test. self-test can be an on-line or off-line function which is initiated by simple subsystem intervention. the drvinh signal selects on-line or off-line testing. the circuit accomplishes the on-line test without accessing the mil-std-1553 data bus by providing an internal data path which connects the encoder circuitry directly to the decoder circuitry. the transceiver is inhibited during this on-line test. the off-line test is designed to include the transceiver as well as the protocol device. this mode will generally be useful as an off-line card test where no live bus is in use. to initiate the self-test a word is placed in the vector word latch, loop test enable ( lten ) is held low, and the loop test trigger ( lttrig ) signal is pulsed low. the primary bus will be tested with the word that resides in the vector word latch, encoded then looped back, decoded and presented to the subsystem as a normal data transfer would be accomplished. the secondary bus is sequentially tested after the primary bus is completed via request bus a (reqbusa) utilizing the same word residing in the vector word latch. upon completion of each test, pass/fail signals will be asserted reporting the results of the test. this test implementation verifies mil-std-1553 protocol compliance; proper sync character, 16 data bits, manchester ii coding, odd parity, contiguous word checking and a bit by bit comparison of the transmitted data. the self-test circuitry increases the fault coverage by insuring that the internal function blocks; encoder, decoder, and internal control circuitry are operating correctly. an effective data pattern to accomplish this is hex aa55 since each bit is toggled, (8 bit internal highway) on a high/low byte basis. the total time required to complete the self-test cycle is 89 microseconds. the loop test enable signal must remain in the low state throughout the diagnostic cycle.
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 10 pin description signal direction signal description rx data 0/1 input positive data in. this should be a ttl description of the positive, half of the manchester code data on the bus. it should be driven to a logic level ?1? when a predetermined positive threshold is exceeded on the bus. rx data 0/1 input negative data in. this should be a ttl description of the negative half of the manchester code data on the bus. it should be driven to a logic level ?1? when a predetermined negative threshold is exceeded on the bus. tx inhibit 0 output transmitter inhibit bus 0. normally high. goes low when the transmitter is transmitting. should be used to inhibit the bus "0" driver. tx inhibit 1 output transmitter inhibit bus 1. normally high. goes low when the transmitter is transmitting. should be used to inhibit the bus "1" driver. tx data output positive data out - when this signal goes high the bus should be driven positive. tx data output negative data out - when this signal goes high the bus should be driven negative. rtad 0-4 input rt address lines - these should be hardwired by the user. rtad4 is the most significant bit. rtadpar input rt address parity line - this must be hardwired by the user to give odd parity. bit decode input built-ln test decode - when held low, prevents resetting txto bit, hsfail bit, and ltfail bit in the bit word (as well as tf and ssf bits in the status word) upon receipt of a transmit bit word mode command. bcsten 0/1 input broadcast command enable bus 0/1 - when low the recognition of broadcast command is prevented on both bus 0 and 1. ct1991 only. bcsten 0 input broadcast command enable bus 0 - when low the recognition of broadcast command is prevented on bus 0. ct1990 only. bcsten 1 input broadcast command enable bus 1 - when low the recognition of broadcast command is prevented on bus 1. ct1990 only. 6mck input 6 megahertz master clock. ih 08 (lsb) ih 19 ih 210 ih 311 ih 412 ih 513 ih614 ih715 (msb) bi-directional internal highway - bi-directional 8 bit highway on which 16 bit words are passed in two bytes. ih 715 is the most significant bit of each byte, the most significant byte being transferred first. the highway should only be driven by the subsystem when data is to be transferred to the rt. dtrq output data transfer request - goes low to request a data transfer between the asic and subsystem. goes high at the end of the transfer. dtak input data transfer acknowledge - goes low to indicate that the subsystem is ready for the data transfer. iustb output interface unit strobe - this is a double pulse strobe used to transfer the two bytes of data h/ l output high/low - indicates which byte of data is on the internal highway. logic level "0" for least significant byte. gbr output good block received - pulses low for 500ns when a block of data has been received by the asic and has passed all the validity and error checks.
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 11 nbgt output new bus grant - pulses low whenever a new command is accepted by the asic. mereq input message error request - positive-going edge will cause message error bit in status word to be set. tx/ rx output transmit/receive - the state of this line informs the subsystem whether it is to transmit or receive data the signal is valid while incmd is low. incmd output in command - goes low when the rt is servicing a valid command. the subaddress and word count lines are valid while the signal is low. wc0-wc4 output word count - these five lines specify the requested number of data words to be received or transmitted. valid when incmd is low. sa0-sa4 output sub address - these five lines are a label for the data being transferred. valid when incmd is low. cwc0-cwc4 output current word count - these five lines define which data word in the message is currently being transferred. sync output synchronize - goes low when a synchronize mode code is being serviced. vecten / dwen output vector word enable/dataword enable - in the rt mode, this signal is provided to enable the contents of the vector word latch (which is situated in the subsystem) onto the asic?s internal highway. this signal, when in the bus controller mode, is used to enable mode code data from the subsystem onto the internal highway. reset output reset - this line pulses low for 500ns on completion of the servicing of a valid and legal mode command to reset remote terminal. sserr input subsystem error - by taking this line low, the subsystem can set the subsystem flag in the status word. busy input busy - this signal should be driven low if the subsystem is not ready to perform a data transfer to or from the asic. servreq input service request - this signal should be driven low to request an asynchronous transfer and left low until the transfer has taken place. inclk output internal clock (2 mhz) - this is made available for synchronization use by the subsystem if required. however, many of the outputs to the subsystem are asynchronous. eot output end of transmission - goes low if a valid sync plus two data bits do not appear in time to be contiguous with preceding word. rtader output remote terminal address error - this line goes low if an error is detected in the rt address parity of the selected receiver. any receiver detecting an error in the rt address will turn itself off. hsfail output handshake failure - this line pulses low if the allowable time for dtak response has been exceeded during the asic/subsystem data transfer handshaking. lstcmd / cwen output last command/command word enable - this line pulses low when servicing a valid and legal mode command to transmit last command. when in rt mode this line must not be used to enable data from the subsystem. this line also pulses low, when in the bus control mode, when a command word is required for transmission. pin description (cont.) signal direction signal description
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 12 staten / statstb output status enable/status strobe - this line pulses low to enable the status word onto the internal highway for transmission. when in rt mode this line must not be used to enable data from the subsystem. this line also pulses high, when in the bus control mode, to strobe received status words into the subsystem. when pasmon is true this line pulses high for command and status words. stat update input status update - when held low, causes tf or ssf to appear in status word response to transmit status or transmit last command issued immediately after fault occurrence biten / rmdstb output built in test enable/receive mode data strobe - this line pulses low when servicing a valid and legal mode command to transmit the internal bit word. this signal is for information only and must not be used to enable data from the subsystem. this line also pulses high when in the bus control mode when mode data is received to be passed to the subsystem and when data is passed to the subsystem during pasmon . dwsync output data word sync - this line goes low if a data word sync and two manchester biphase bits are valid. ct1990 only. enable input enable - when held low, enables bit decode, next status, and status update program lines. cmsync output command word sync - this line goes low if a command word sync and two manchester biphase bits are valid. ct1990 only. ndrq output no data required - this line goes low if the encoder transmit buffer is full i.e. another word is going to be transmitted. this signal is for information only and must not be used to enable data from the subsystem. next stat input next status - when held low, causes tf or ssf to appear in very next status word after fault occurrence (except for transmit status or transmit last com- mand). pasmon input passive monitor - when functioning as a bus controller this line acts as a passive monitor select. the active going edge of this line will cause the reqbus lines to be latched and that bus, now selected will be monitored so long as pasmon remains low. all traffic on the bus will be handed, after validation, to the subsystem via statstb for status and commands words, and rmdstb for data words. bcopstb input bus controller operation strobe - when functioning as a bus controller a low going pulse on this line will initiate the selected bus controller operation on the requested bus, using bcopa&b and reqbusa&b. rmdstb see biten /rmdstb. bcopa input bus control operation a - least significant bit of the bus controller operation select lines. bcopb input bus control operation b - most significant bit of the bus controller operation select lines. reqbus a bi-directional request bus a - this line, when in rt mode, is the least significant bit of the bus request lines which specify the origin of the command, i.e. they are sources. when in bc mode these lines are sinks and specify which bus is to be used for the next command. reqbus b bi-directional request bus b - most significant bit of the bus request lines. (see above for description.) pin description (cont.) signal direction signal description
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 13 rt/ bc input remote terminal/bus control - this line when high causes the asic to function as a remote terminal. when low the asic functions as a bus controller or passive monitor. dbcacc input dynamic bus control accept - this line should be permanently tied low if a subsystem is able to accept control of the bus if offered. ltfail output loop test fail - this line goes low if any error in the transmitted waveform is detected or if any parity error in the hardwired rt address is detected. error output error - this line latches low if a manchester or parity error is detected. it is reset by the next cmsync (rt mode) and also by rto in the bc mode. rto output reply time out - this signal will pulse low whenever the reply time for a transmitting terminal has been exceeded. this line is intended for the bus controller use. txto output transmitter time ou t - this line goes true if the transmitter time out limits are exceeded. parer output parity error - this line will pulse low if a parity error is detected by the decoder. maner output manchester error - this line will pulse low if a manchester error is detected by the decoder. dbcreq output dynamic bus control request - this line will pulse low when the status reply for a mode code dynamic bus control has finished where the accept bit was set. vald output valid data - this line will pulse low when a valid data word is received. drvinh input driver inhibit - selects on-line or off-line testing during automated self test. when high self test is on-line. must be high when lten is high. ct1991 only. lten input loop test enable - enables automated self-test when low. normally high. ct1991 only. lttrig input loop test trigger - when pulsed low while lten is low automated self-test is initiated. lten pulse width should be 100ns < pw < 5s. ct1991 only. pin description (cont.) signal direction signal description
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 14 next controller to rt transfer receive command data word data word . . . . data word . . status word command word rt to controller transfer next transmit command . . status word data word data word . . . . data word command word next rt to rt transfer receive command transmit command . . status word data word data word . . . . data word . . status word command word mode command without data word next mode command . . status word command word mode command with data word (transmit) next mode command . . status word data word command word mode command with data word (receive) next mode command data word . . status word command word note: = intermessage gap . . = response time figure 1 ? typical message formats t/r bit mode code function associated data word broadcast command allowed 1 00000 dynamic bus control no no 1 00001 synchronize no yes 1 00010 transmit status word no no 1 00011 initiate self test no yes 1 00100 transmitter shutdown no yes 1 00101 override transmitter shutdown no yes 1 00110 inhibit terminal flag bit no yes 1 00111 override lnhibit terminal flag bit no yes 1 01000 reset remote terminal no yes 1 01001 reserved no tbd 1 01111 reserved no tbd 1 10000 transmit vector word yes no 0 10001 synchronize yes yes 1 10010 transmit last command yes no 1 10011 transmit bltword yes no 0 10100 selected transmitter shutdown yes yes 0 10101 override selected transmitter shutdown yes yes 1 or 0 10110 reserved yes tbd 1 or 0 11111 reserved yes tbd figure 2 ? assigned mode codes
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 15 bit times 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 command word 5 1 5 5 1 sync remote terminal address t/r subaddress/mode data word count/mode code p data word 16 1 data p 1 lsb 20 bit word 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 p sync status word 5 1 1 1 3 1 1 1 1 1 1 sync remote terminal address reserved note: t/r ? transmit/receive p ? parity t r a n s m i t t e r t i m e o u t o n b u s 3 t r a n s m i t t e r t i m e o u t o n b u s 2 t r a n s m i t t e r t i m e o u t o n b u s 1 t r a n s m i t t e r t i m e o u t o n b u s 0 b u s 3 s h u t d o w n b u s 2 s h u t d o w n b u s 1 s h u t d o w n b u s 0 s h u t d o w n b r o a d c a s t t r a n s m i t d a t a r e c e i v e d w o r d c o u n t h i g h w o r d c o u n t l o w i l l e g a l m o d e c o m m a n d m o d e t / r b i t w r o n g l o o p t e s t f a i l u r e s u b s y s t e m h a n d s h a k e f a i l u r e t r a n s m i t t e r t i m e o u t f l a g m e s s a g e e r r o r i n s t r u m e n t a t i o n s e r v i c e r e q u e s t b r o a d c a s t c o m m a n d r e c e i v e d b u s y s u b s y s t e m f l a g d y n a m i c b u s c o n t r o l a c c e p t a n c e t e r m i n a l f l a g p a r i t y figure 3 ? word count
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 16 1553b bus "b" 1553b bus "a" act4453 driver/ receiver 1 act4453 driver/ receiver 0 tx data out rx data in tx data out rx data in xfr0 xfr1 + + tx data out rx data in tx data out rx data in rx data out tx data in tx data in rx data out rx data out tx data in tx data in rx data out tx inhibit "1" ct1990/1 rx data 0 rx data 0 tx data tx data tx inhibit "0" tx inhibit "1" tx inhibit "0" figure 5 ? example of an interface between the ct1990/1 and driver/receiver 1mhz nrz manchester figure 4 ? data encoding data = bi-phase clock (+) - (0) - (+) - (0) - (+) - (0) - (-) - one bit time rx data 1 rx data 1
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 17 figure 6 ? transfer of three data words from rt 03 to bc pdin nbgt incmd dtrq iustb h/ l gbr eot pdin nbgt incmd dtrq iustb h/ l gbr eot figure 7 ? transfer of two data words from bc to rt 03 pdin nbgt incmd dtrq iustb h/ l reset eot figure 8 ? mode command reset remote terminal
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 18 figure 10 ? rt to rt transfer of four data words (this rt receiving the data) pdin nbgt incmd dtrq iustb h/ l gbr eot figure 9 ? rt to rt transfer of four data words (this rt sending the data) pdin nbgt incmd dtrq iustb h/ l gbr eot
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 19 dtak iustb h/ l cwc0-cwc4 dtrq subsystem reply time < 13.5s don?t care 250 nsec 250 nsec 500 nsec valid incremented enable high byte of tx data on internal highway enable low byte of tx data on internal highway figure 11 ? handshaking for tx data transfers dtak iustb h/ l cwc0-cwc4 dtrq subsystem reply time < 1.5s don?t care 250 nsec 250 nsec 500 nsec incremented valid low byte valid high byte valid internal highway figure 12 ? handshaking for rx data transfers
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 20 sa4-sa0 nbgt 1.0s minimum valid valid valid previous command value previous command value previous command value busy latch here tx/ rx wc4-wc0 cwc4-cwc0 incmd inclk figure 13 ? new command initialization nbgt incmd vecten h/ l enable high byte of vector word onto internal highway enable low byte of vector word onto internal highway figure 14 ? transmit vector word command } 1.5s approx. }
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 21 pdin nbgt incmd sync ilustb eot wc4 h/ l 0 0 0 1 1 1 1 1 1 1 0 0 0 0 0 1 0 figure 15 ? synchronize (with data) mode command pdin nbgt incmd sync eot wc0 0 0 0 1 1 1 1 1 1 0 0 0 0 1 0 iustb figure 16 ? synchronize (no data) mode command
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 22 b c o p s t b n d r g c w e n h / l i u s t b c / d n b g t i n c m d v a l c v a l d s t a t s t b d t r g g b r e o t r t o p d i n f i g u r e 1 7 ? b u s c o n t r o l l e r s e n d i n g c o m m a n d t o r t 1 0 0 0 1 t o t r a n s m i t t w o d a t a w o r d s
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 23 b c o p s t b n d r g c w e n h / l i u s t b c / d n b g t i n c m d v a l c v a l d s t a t s t b d t r g g b r e o t r t o p d i n f i g u r e 1 8 ? b u s c o n t r o l l e r s e n d i n g c o m m a n d t o r t 1 0 0 0 1 t o r e c e i v e t w o d a t a w o r d s
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 24 b c o p s t b b c o p a b c o p b n d r g c w e n h / l i u s t b c / d t x s t b n b g t i n c m d v a l c v a l d s t a t s t b d t r g c w c 0 c w c 1 t r e q g b r e o t t x e n p d o u t r t o i h 7 1 5 i h 6 1 4 i h 6 1 3 i h 4 1 2 i h 3 1 1 i h 2 1 0 i h 1 9 i h 0 6 p d i n f i g u r e 1 9 ? b u s c o n t r o l l e r c o m m a n d i n g r t 1 0 0 0 1 t o t r a n s m i t t w o d a t a w o r d s a t r t 0 0 0 0 1
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 25 bcopstb ndrq h/ l statstb bcopb pdin bcopa cwen txstb bcopstb h/ l bcopb pdin bcopa cwen dwen dwen bcopstb h/ l bcopb pdin bcopa statstb rmdstb figure 20 ? bus controller sending mode command transmit status word mode code 00010 figure 21 ? bus controller sending mode command synchronize mode code 10001 figure 22 ? bus controller sending mode command transmit vector mode code 10000
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 26 pin out description - ct1990 pin # function pin # function pin # function 1 bit decode 31 reqbusb 61 error 2 cwc0 (lsb) 32 reqbusa 62 ltfail 3 sa4 (msb) 33 common & case 63 maner 4 sa3 34 enable 64 parer 5 sa2 35 stat update 65 vald 6 cwc4 (msb) 36 mereq 66 rtader 7 cwc3 37 ih 08 (lsb) 67 rx data 1 8 cwc2 38 ih19 68 rx data 1 9 cwc1 39 ih210 69 +5 vin 10 gbr 40 ih311 70 tx inhibit 1 11 h/ l 41 ih412 71 tx inhibit 0 12 staten /statstb 42 ih513 72 tx data 13 eot 43 ih614 73 tx data 14 sa1 44 ih715 (msb) 74 servreq 15 sa0 (lsb) 45 nc 75 txto 16 incmd 46 nc 76 dbcacc 17 tx/ rx 47 rtadpar 77 reset 18 dtrq 48 rtad0 (lsb) 78 rt/ bc 19 vecten / dwen 49 rtad1 79 dbcreq 20 nbgt 50 rtad2 80 hsfail 21 sync 51 rtad3 81 lstcmd / cwen 22 inclk 52 rtad4 (msb) 82 biten / rmdstb 23 iustb 53 cmsync 83 busy 24 next stat 54 dwsync 84 wc4 (msb) 25 dtak 55 bcsten 0 85 wc3 26 bcopa 56 rx data 0 86 wc0 (lsb) 27 bcopstb 57 rx data 0 87 sserr 28 bcopb 58 bcsten 1 88 wc2 29 pasmon 59 rto 89 wc1 30 ndrq 60 6 mck 90 nc
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 27 pin out description - ct1991 pin # function pin # function pin # function 1 bit decode 31 reqbusb 61 error 2 cwc0 (lsb) 32 reqbusa 62 ltfail 3 sa4 (msb) 33 common & case 63 maner 4 sa3 34 enable 64 parer 5 sa2 35 stat update 65 vald 6 cwc4 (msb) 36 mereq 66 rtader 7 cwc3 37 ih 08 (lsb) 67 rx data 1 8 cwc2 38 ih19 68 rx data 1 9 cwc1 39 ih210 69 +5 vin 10 gbr 40 ih311 70 tx inhibit 1 11 h/ l 41 ih412 71 tx inhibit 0 12 staten /statstb 42 ih513 72 tx data 13 eot 43 ih614 73 tx data 14 sa1 44 ih715 (msb) 74 servreq 15 sa0 (lsb) 45 nc 75 txto 16 incmd 46 nc 76 dbcacc 17 tx/ rx 47 rtadpar 77 reset 18 dtrq 48 rtad0 (lsb) 78 rt/ bc 19 vecten / dwen 49 rtad1 79 dbcreq 20 nbgt 50 rtad2 80 hsfail 21 sync 51 rtad3 81 lstcmd / cwen 22 inclk 52 rtad4 (msb) 82 biten / rmdstb 23 iustb 53 lten 83 busy 24 next stat 54 lttrig 84 wc4 (msb) 25 dtak 55 bcsten 0/1 85 wc3 26 bcopa 56 rx data 0 86 wc0 (lsb) 27 bcopstb 57 rx data 0 87 sserr 28 bcopb 58 drvinh 88 wc2 29 pasmon 59 rto 89 wc1 30 ndrq 60 6 mck 90 nc
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 28 ceramic cofired plug in package outline lead 1 & esd designator .100 1.100 typ 2.200 2.100 pin 43 pin 45 pin 44 pin 2 pin 3 .135 .050 typ 1.300 .090 .135 pin 1 pin 48 pin 46 pin 47 pin 88 pin 90 pin 89 .018 dia typ 2.400 max 1.600 max .200 min .225 max
aeroflex circuit technology scdct1990 rev b 8/21/00 plainview ny (516) 694-6700 29 ordering information model number desc part number package CT1990-1-20 5962-9477501 1.6" x 2.4" ceramic plug in ct1991-1-20 pending 1.6" x 2.4" ceramic plug in circuit technology specifications subject to change without notice. aeroflex circuit technology 35 south service road plainview new york 11830 telephone: (516) 694-6700 fax: (516) 694-6715 toll free inquiries: 1-(800)the-1553

▲Up To Search▲

Price & Availability of CT1990-1-20

	To Download CT1990-1-20 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .